Skip to content

Conversation

@fersilva16
Copy link

This pull request introduces string references for GraphQL types, which aims to solve the problem with circular dependency between types in multiple files. Here's an usage example:

type: new GraphQLNonNull(new GraphQLList(new GraphQLNonNull('User')))

This PR has only the implementation for output types for now.

I've also made a RFC repository with a patch and pratical examples for testing: https://github.com/fersilva16/graphql-refs-rfc

Contributions and feedback are welcome.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Dec 10, 2023

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: fersilva16 / name: Fernando Silva (602fe1c)

@netlify
Copy link

netlify bot commented Dec 10, 2023

Deploy Preview for compassionate-pike-271cb3 ready!

Name Link
🔨 Latest commit 602fe1c
🔍 Latest deploy log https://app.netlify.com/sites/compassionate-pike-271cb3/deploys/65762522e405480008550690
😎 Deploy Preview https://deploy-preview-3995--compassionate-pike-271cb3.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@daniloab
Copy link

daniloab commented Aug 6, 2024

How could we move forward with this pr?

@yaacovCR
Copy link
Contributor

yaacovCR commented Oct 1, 2024

This was discussed at the GraphQL JS WG meeting on March 27 per the notes.

Summarizing from my recollection, I think this PR was felt to be a reasonable alternative, but the question was how is it better than the current option of using thunks, and balancing the desire for flexibility vs. reducing maintenance burden by having a canonical way of doing things.

I am going to close this for now, feel free to reopen as needed.

@yaacovCR yaacovCR closed this Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants